Conversation
|
I think I was able to get it to work with the clang + openmp by replacing (in setup.py): ext.extra_compile_args.extend(["-fopenmp"])
ext.extra_link_args.extend(["-fopenmp"])with # OpenMP support: macOS with Apple clang requires different flags
if sys.platform == "darwin":
# Check if using Apple clang (doesn't support -fopenmp directly)
# Use -Xpreprocessor -fopenmp with libomp from Homebrew
libomp_prefix = os.environ.get(
"LIBOMP_PREFIX", "/opt/homebrew/opt/libomp"
)
ext.include_dirs.append(os.path.join(libomp_prefix, "include"))
ext.library_dirs.append(os.path.join(libomp_prefix, "lib"))
ext.extra_compile_args.extend(["-Xpreprocessor", "-fopenmp"])
ext.extra_link_args.extend(["-lomp"])
else:
ext.extra_compile_args.extend(["-fopenmp"])
ext.extra_link_args.extend(["-fopenmp"]) |
|
Just so I understand: is this for the case that the user has done Basically, my understanding/guess is that to use LLVM Clang, one is supposed to use |
|
Yes I think that's right! Or at least, that's my current understanding :) |
|
The |
|
Failure I think is because of a gaia archive downtime? |
2 participants
Not sure if we also need to instruct people to set
CCandCXXto the LLVM compiler, or if it will be the default. @adrn maybe you could test this?